Stipulations vs. To-Dos

Overview

To-Dos and Stipulations are able to be created by writing rule logic. While Stipulations are also able to be added manually, To-Dos can only be called by rule logic. Stipulations can be created in various rule categories, such as Stipulations, Event Processing and Decisioning. To-Do logic can only be written in the Validation category. If Stipulations are added in a Validation rule, they do not generate as intended.

When writing rules, authors are able to create rules that require To-Dos or Stipulations to be fulfilled prior to Approval or Disbursement. However if rule logic is faulty, the Loan Origination module may not be able to assign the desired To-Do or Stipulation to an application. Considering rules containing To-Dos and Stipulations are vital for driving an application, the Framework’s non-action could cause required actions and information to be missed.

Rule Logic

The following example demonstrates incorrect rule logic:

This rule logic is flawed as it instructs the system to add a To-Do and a Stipulation prior to rendering a decision, when the qualifying logic in the If Statement requires a decision to already be rendered. Additionally, the Validation rule category is not able to add Stipulations to an application.

When writing rule logic, be certain the If Statement does not disqualify the logic in the Then Statement. For instance, if the If Statement contains logic such as “If Decision has a status of Approved or LO Approve, a To-Do or Stipulation that is required for Approval cannot be added as a decision has already been rendered. If a rule using this faulty logic has been written and implemented, it does not work as intended. The system deletes the To-Do or Stipulation and creates an entry in the error log to capture the deletion. This behavior is similar for rules generating Stipulations.

The Event Log does not capture the dismissed Stipulation from the rule example above as it was written under the wrong rule category.